Providing compliance enforcement for manually dialed wireless numbers in a contact center

ABSTRACT

Systems and methods are disclosed for originating a call to a wireless number by a contact center while enforcing various compliance requirements. In one embodiment, a compliance server and a PBX cooperate to originate the call to the wireless number. The agent logs into the compliance server and the compliance server provides the agent with a wireless number to dial. The agent manually enters the wireless number using a phone connected to the PBX. The PBX queries the compliance server regarding establishing the wireless call. Upon authorization, the PBX establishes a first call leg to the compliance server, and a second call leg to the called party that is joined with the call leg to the agent&#39;s phone. Upon completion of the call, the agent dispositions the call to the compliance server, which then releases the first call leg. In response, the PBX then releases the second call leg.

RELATED APPLICATIONS

This application claims priority to provisional U.S. patent applicationNo. 61/813,713, entitled “Compliance Enforcement for Manually DialedWireless Numbers in a Contact Center,” which was filed on Apr. 19, 2013and the contents of which are incorporated by reference for all that itteaches.

FIELD OF THE DISCLOSURE

The concepts and technologies disclosed herein generally pertain toenforcement of compliance requirements for calls directed to wirelesstelephone numbers wherein the calls are originated by agents in acontact center.

BACKGROUND OF THE INVENTION

The Telephone Consumer Protection Act (“TCPA”) passed in 1991 regulates,in part, aspects of originating certain types of telephone calls.Specifically, the TCPA statute and Federal Communications Commission's(“FCC”) regulations interpreting the TCPA prohibit the use of an“autodialer” to place calls to certain types of telephone numbers(simply referred to as “numbers” herein), including calls to any number“assigned to a paging service, cellular telephone service, specializedmobile radio service, or other radio common carrier service, or anyservice for which the called party is charged for the call.” 47 U.S.C.§227(b) (1) (A); 47 C.F.R. §64.1200(a)(1). This covers what is commonlyreferred to as a “wireless number” that is assigned to a mobile phone.For simplicity, this term (“wireless number”) is used herein to refer tonumbers that cannot be called under the TCPA using an autodialer.

The FCC regulates aspects of the TCPA and has considered the scope ofthe term “autodialer.” The TCPA and FCC's rules have defined an“automatic telephone dialing system” (“autodialer”) as “equipment whichhas the capacity (A) to store or produce telephone numbers to be called,using a random or sequential number generator; and (B) to dial suchnumbers.” U.S.C. §227(a) (1). At the time the statute was passed,dialers were frequently configured to originate calls by dialing arandom telephone number or dialing telephone numbers in sequence (e.g.,404 555-0000 through 404 555-9999). Hence, the definition of anautodialer incorporated aspects of processing telephone numbers using arandom or sequential number generator.

Over time, the FCC has interpreted the scope of an “autodialer” toinclude equipment that “need only have the capacity to store or producetelephone numbers.” (See Rules and Regulations Implementing theTelephone Consumer Protection Act of 1991, Report and Order, 18 FCC Rcd.14014 ¶133 (2003)). Coincident with this time period, predictive dialerswere increasingly being used to originate calls to wireline numbers.Predictive dialers can originate calls using a list of numbers to becalled with reduced agent waiting time. There is little debate that manypredictive dialers do not use “random or sequential number generators.”However, the FCC has classified predictive dialers as “autodialers” incertain instances to ensure that the prohibition on autodialed calls wasnot circumvented by automatically dialing “lists of numbers” instead ofcreating and dialing 10 digit telephone numbers arbitrarily. The FCC hasviewed a basic function of an autodialer as equipment having the“capacity to dial numbers without human intervention.” Id. ¶131. Thus,it appears that equipment having the capacity to dial number withouthuman intervention may be an autodialer, regardless of whether suchequipment is actually used in such a manner.

As can be expected, it is not always clear whether an equipmentconfiguration is considered an “autodialer.” Thus, the problem addressedby the present disclosure is ensuring that compliance relatedregulations and policies are adhered to while also complying with themandate that prohibits the use of “autodialers” to call wirelessnumbers. It is against this backdrop that the concepts and technologiesdisclosed herein are presented.

SUMMARY

Various embodiments are disclosed for providing compliance enforcementin a contact center when an agent originates a call to a wirelessnumber. In various embodiments, a compliance server and PBX cooperate toallow manual dialing by the agent using the PBX, while allowing thecompliance server to ensure that various compliance regulations and/orpolicies are adhered to in conjunction with originating the wirelesscall. The compliance server is able to maintain status informationassociated with the agent and/or the wireless call, even though thecompliance server itself does not originate the call.

In one embodiment, coordination is provided between the PBX and thecompliance server so as to provide compliance enforcement when dialing awireless number. The coordination may involve various types of signalingbetween the PBX and the compliance server. Specifically, in oneembodiment, the compliance server provides compliance enforcement byresponding to a query from the PBX regarding a call to a wireless numberdialed by the agent. In other embodiments, coordination between the PBXand a compliance module occurs within a single processing system so asto provide compliance enforcement when dialing a wireless number.

As is discussed in greater detail below, the subject matter disclosedherein may be implemented as a computer-controlled apparatus, a method,a computing system, or as an article of manufacture such as a tangible,non-transitory computer-readable storage medium. These and various otherfeatures will be apparent from the following Detailed Description andthe associated drawings.

This Summary is provided to exemplify concepts at a high level form thatare further described below in the Detailed Description. This Summary isnot intended to identify key or essential features of the claimedsubject matter, nor is it intended that this Summary be used to limitthe scope of the claimed subject matter. Furthermore, the claimedsubject matter is not limited to implementations that address any or alldisadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates one embodiment of a contact center architectureincorporating a compliance server providing compliance enforcement whenan agent originates a call to a wireless number.

FIG. 2 illustrates one embodiment of an architecture comprising acompliance server and a PBX in a contact center used to providecompliance enforcement when an agent originates a call to a wirelessnumber.

FIG. 3 illustrates one embodiment of a message flow between variouscomponents for providing compliance enforcement when originating a callto a wireless number.

FIGS. 4A and 4B illustrate one embodiment of a process flow of thecompliance server when used for providing compliance enforcement.

FIG. 5 illustrates another embodiment of a message flow between variouscomponents for providing compliance enforcement when originating a callto a wireless number.

FIG. 6 illustrates another embodiment of a process flow of thecompliance server when used for providing compliance enforcement.

FIG. 7 illustrates another embodiment of an architecture comprising aPBX in a contact center used for providing compliance enforcement whenan agent originates a call to a wireless number.

FIGS. 8-9 illustrate additional embodiments of a message flow betweenvarious components for providing compliance enforcement when originatinga call to a wireless number

FIG. 10 illustrates one embodiment of a system architecture of acompliance server or a PBX used to embody the concepts and technologiesdisclosed herein.

DETAILED DESCRIPTION

Predictive dialers are often used to generate calls by dialing aplurality of wireline telephone numbers with the expectation that many,if not most, calls will not be answered by the desired party. Many callsoriginated by the predictive dialer expect to be unanswered, answered byan answering machine, forwarded to a voice mail system, or disconnected.Other conditions may be encountered where the call is not answered bythe desired party. Rather than consume an agent's time by originatingcalls in a serial manner and encountering the above conditions, thepredictive dialer will dial a number of calls simultaneously. When acall is answered by a party, that call is connected to an agent who canthen speak with the party. Thus, the agent has less wait time beforetalking to the right party. Predictive dialers allow the agent's time tobe used with greater efficiency and offer many advantages over the agentmanually dialing the call.

As with any technology, there is the possibility of misuse. Variousregulations have been developed to ensure that contact center operatorsdo not abuse the usage of predictive dialers thereby creating anunreasonable nuisance to the public. For example, when a predictivedialer determines that an agent is available, it can simultaneouslygenerate a large number of outgoing calls using telephone numbers on adialing list. The first call that is answered by a person may beconnected to the available agent. However, if there are no otheravailable agents, then the remaining calls that are answered will not beimmediately connected to an agent. Under such circumstances, thepredictive dialer may simply hang up when the called party answers orplay an announcement asking the called party to wait for the nextavailable agent. However, this practice is generally deemed undesirableand federal regulations may limit the abandonment rate of a contactcenter when operating a predictive dialer.

Another potential undesirable aspect involves re-dialing an abandonedcall. In the above example, if a call is answered, but no agent isavailable, the predictive dialer may simply terminate the call. Thus,the called party may rush to answer the phone, only to hear silence. Thenumber may be flagged by the predictive dialer as being unanswered andincluded in the next dialing attempt when the next agent is available.This process may be repeated a number of times during a day. Without anysafeguards in place, it is possible to repeatedly call the same numberand repeatedly hang up, further aggravating the called party. Even ifthe called party is not home, this mode of operation can result in thecalled party's caller-ID feature on their telephone to record a largenumber of consecutive call attempts by the predictive dialer. Suchrepeated call attempts by themselves may be deemed harassing, and mayviolate federal regulations in certain circumstances. In many instances,large fines may be assessed against the call center operator.

Thus, there are various compliance related aspects that must be enforcedduring a campaign when originating calls. As used herein, “compliancerequirements” may include state regulatory requirements, federalregulatory requirements, contact center policies, or clientrequirements. Thus, a variety of restrictions or limitations on callorigination may fall within the scope of compliance requirements.

Some of the compliance related aspects are described below, whichinclude some of those previously mentioned:

-   -   Target Abandonment Rate: Various state and/or federal        abandonment rates may have to be complied with. An abandoned        call may be defined as a call answered by a person, but which is        not connected to an agent within two seconds. The actual        abandonment rate may be measured over a set time period for a        particular campaign, and cannot exceed a given percentage of        calls as defined by the governing abandonment rate.    -   Attempt Counter: A limit may be defined for the number of call        attempts that can be made to a number over a time period (e.g.,        day, week, or month), as well as the minimum time period that        must occur between call attempts.    -   Identification Message: If a party answers a call, they should        be connected to an agent within a set amount of time (2 seconds)        and if this is not possible, then the party should be presented        with an identification message prior to the dialer abandoning        the call or with a message for the next available agent.    -   Call Screening: Telephone numbers may be defined in various        databases as being excluded from certain types of calls. These        databases are frequently termed “do-not-call” databases or        “do-not-call lists” and may be national, state, or        business-specific in scope. Other do-not call databases may        identify numbers as wireless numbers, as these may be excluded        from being called for certain purposes. In some instances,        exceptions may exist where the party has authorized contact        despite being included on one of the do-not-call lists. Further,        a party may provide authorization to be called on one number        (e.g., a home number), but not on another number (e.g., a        wireless or work number).    -   Calling Window: Call originations may be limited to occur within        certain time periods relative to the local time of the called        party. For example, calls may be limited between 8:00 a.m. and        9:00 p.m. according to the local time of the called party. This        may require using the called telephone number and/or account        records to ascertain the appropriate location and time zone of        the called party. In the case of wireless numbers, which are        mobile, it may be difficult to ascertain which time zone or        geography where the called party is located in.    -   Call Recording/Call Recording Exclusion: Depending on the state,        certain calls may be recorded without the called party's consent        to aid in quality control or to ensure that certain compliance        requirements are met. On the other hand, certain states do allow        recording without the called party's consent. This may be        further impacted based on the statutes of the state where the        call originated from as well as the state the called party is        located in.    -   Alternate Number Dialing: If a call to a party is unanswered,        then alternative numbers associated with that party may be used.        However, various conditions and requirements may be associated        with the usage of these alternate numbers, since the conditions        and requirements associated with using the first number are not        necessary applicable for using the alternative number.    -   State Specific Reporting Requirements: Calls originating from,        or terminating to, a given state may have state-specific        reporting requirements.    -   Contact Center Specific Policies: A contact center may modify        any of the above requirements to make the requirements more        restrictive. For example, whereas certain regulations may limit        calls between 8:00 a.m. and 9:00 p.m., a contact center may        chose to prohibit calls before 9:00 a.m.    -   The application of the above compliance requirements may depend        on the purpose and nature of the call, or whether there is any        form of pre-existing relationship between the parties.

The list of compliance requirements provided above is illustrative andis not intended to be exhaustive. Some of these requirements may beapplicable for dialing wireless numbers under certain context forcertain regulations, whereas other requirements may be applicable forother types of numbers or other regulations. Other requirements may beapplicable and may be regulated by the contact center itself (viainternal contact center policies), or by local, state, or federalgovernment regulations.

The above demonstrates that there is a complex set of compliancerequirements that may be applicable when dialing a telephone number.Additionally, when dialing a wireless number, additional compliancerequirements may apply. Specifically, certain prohibitions apply whendialing a wireless number, e.g., wireless numbers should not be dialedby an “autodialer.” Complicating matters is that it is not alwaysreadily possible to detect with certainty by examining the telephonenumber itself whether it is a wireline number or a wireless number. Forexample, years ago wireless numbers were allocated using a unique areacode and office code (e.g., “NPA-NXX” or the first six digits of a tendigit telephone number). Thus, individuals familiar with telephonenumbers in a local area could ascertain whether a telephone number waswireless or wireline by examining the NPX-NXX portion of the telephonenumber. However, that typically is no longer the case as an NPX-NXX maybe allocated to both wireline and wireless numbers. Since contactcenters may originate calls to any location in the United States, it isunreasonable to expect an agent to be familiar with local telephonenumbers. Further, a wireline telephone number can be ported to awireless service provider. Consequently, it is generally not feasiblefor an agent to determine by examining the telephone number itselfwhether it is a wireline or wireless number.

Having an agent manually dial a wireless number may avoid theprohibition of using an “autodialer.” For purposes herein, “manuallydialing” refers to the agent indicating on a digit-by-digit basis thetelephone number to a device which originates the call, and it can beassumed that the device does not “store or produce” the number dialed,and otherwise avoids the requirements for an “autodialer.” In someembodiments, the agent may request that the numbers be dialed. In oneembodiment, the device could be a PBX that can be used to manually diala number and is generally considered to be outside the scope of an“autodialer.”

However, having an agent manually dial a number increases the risk offailing to comply with current or future compliance requirements. Forexample, a predictive dialer can ensure that restrictions are met inregard to:

-   -   dialing a number during certain hours of the day per the local        time zone of the called party,    -   limiting the number of attempts per telephone number,        individual, or account holder,    -   limiting the number of messages left (voice mail or answering        machine messages) associated with a telephone number, and    -   ensuring there is a minimum amount of time between call attempts        per telephone number, individual, or account holder.

Relying on human operator skill to meet all the applicable compliancerequirements is likely to result in a compliance violation sooner orlater. For example, an agent in a contact center may be located in theEastern Time zone. At 9:00 a.m. in the Eastern Time zone, it is 6:00a.m. in the Pacific Time zone. Regulations may allow the agent to dial anumber terminating in the Eastern Time zone, but not in the Pacific Timezone. Given a particular number, it may be difficult for the agent toknow what time zone the called party is in. While this may be manuallydetermined, computerized approaches are faster and more accurate.Predictive dialers have safeguards that ascertain the time zone of thetarget telephone number, and/or compare this with the correspondingperson's residential location to determine whether the call can beoriginated. An agent may make an error and call an individual in thePacific Time zone at 6:00 a.m.

Further complicating meeting the compliance requirements is thattypically a group of agents is involved in dialing the target parties.Coordination between agents is required, so that duplicative efforts areavoided. It is easy to imagine various scenarios where this can occur,including for example, where an agent dials a target party and leaves amessage and is shortly followed by another agent calling that samenumber and leaving another message. In certain contexts, the resultcould be deemed harassment.

Further, the set of requirements that are applicable to dialing aparticular call may change in the future. Additional regulations may beimposed, as well as changing contact center policies may have to beadhered to. Thus, the challenge is how to ensure that manually dialedcalls to wireless numbers by agents in a contact center are stillsubjected to compliance enforcement. Further, the infrastructure shouldbe adaptable to future or changing requirements. While dialers are wellsuited for processing a number to enforce compliance aspects, theycannot be used to dial the wireless number itself in certain situations,in light of some interpretations of the applicable statutes and FCCregulations. Thus, an approach is required for coordinating thecompliance enforcement mechanisms in a dialer with calls established bythe PBX.

Contact Center Context

FIG. 1 shows one embodiment of a contact center architecture 100illustrating the various technologies disclosed herein. Although manyaspects of contact center operations are disclosed herein in the contextof voice calls, the contact center may process other forms ofcommunication such as facsimiles, emails, text messages, video calls,chat messages, and other forms. The term “party” without any furtherqualification refers to a live person (as opposed to an answeringmachine or voice mail service) associated with an instance ofcommunication originated by the contact center.

The contact center shown in FIG. 1 may process voice calls that areoriginated by a dialer 155. The dialer 155 is typically configured todial a list of telephone numbers to initiate outbound calls. The list oftelephone numbers may be stored in a data store 175 that is accessibleusing a local network 170. The dialer 155 may directly interface withvoice trunks using facilities 116 d to the PSTN 115 for originatingcalls. After the calls are originated, a transfer or connect operationby the dialer 155 may connect the call with an agent, or place the callin a queue for a next available agent. In the latter case, announcementsor music may be provided to the party while they are waiting.

In various embodiments, the dialer 155 may be a predictive dialer thatmakes use of one or more pacing algorithms to determine how and when todial a list of numbers so as to minimize the likelihood of a calledparty being placed in a queue while maintaining effective agentutilization. The dialer 155 may “dial ahead” by originating more callsthan there are available agents, expecting that some calls will not beanswered by live parties, or that an agent may become available in time.The dialer 155 also ensures that applicable compliance requirements areenforced.

Outbound voice calls may originate from the contact center to partiesusing a variety of phone types. A party may receive a call at aconventional analog telephone 110 b connected to a public switchedtelephone network (“PSTN”) 115 using an analog plain old telephoneservice (“POTS”) line 116 a. The call may be routed by the dialer to thePSTN 115 and may comprise various types of facilities, including, butnot limited to: T1 trunks, SONET based fiber optic networks, ATMnetworks, PSTN trunks 116 d. The dialer may also route calls to othernetworks, such as the Internet 123 a, 123 b using facilities 116 e, 116c.

Voice calls may also be received at a mobile device 110 c, such as asmart phone or tablet, which wirelessly communicates with a mobileservice provider (“MSP”) 112. The voice calls may be routed to the PSTN115 using an integrated services digital network (“ISDN”) interface 116b or other types of interfaces that are well known to those skilled inthe art. The MSP 112 may also handle calls as packetized voice, referredto herein as voice-over-IP (“VoIP”) to an Internet provider 123 b usingInternet-based protocols. For convenience, unless indicated otherwise,the term “trunk” refers to any type of communication facility providingvoice calls to, or from, the contact center, regardless of the type ofprotocol or technology used. Specifically, a “trunk” as referred toherein is not limited to time-division multiplexing (“TDM”) technology.

Voice calls may also be received by a party employing a so-called “IPphone,” “VoIP phone,” or “soft phone” 110 a. In one embodiment, the softphone may comprise a computing device 105, such as a laptop, desktop, orcomputing tablet, which interfaces with a headphone/microphonecombination, also referred to as a “headset” 106. An IP phone may use adigital voice control protocol and may process packetized voice dataaccording to various Internet based voice protocols, such as sessioninitiated protocol (“SIP”). The call may be conveyed by other types ofInternet providers 123 a, such as a cable company providing Internetaccess services over a coaxial cable facility 116 e. Those skilled inthe art will recognize that a variety of protocols and facilities may beused to convey voice calls.

In the contact center, calls may be routed over facilities 165 to agentsfor servicing. These facilities may be time division multiplexed (“TDM”)or voice over IP (“VoIP”) based. After a call is originated by thedialer 155 and a called party answers, the call may be connected with anagent using facilities 165. The physical area at which the agent sits isoften referred to as the agent's “position” and these positions areoften grouped into clusters that are managed by a supervisor, who maymonitor calls and the agents' productivity. An agent usually uses acomputing device, such as a computer 160 a-160 c and a voice device 161a-161 c. The combination of computer and voice device may be referred toas a “workstation.” Thus, the workstation collectively has a datacapability and a voice capability, though separate devices may be used.In some instances, “workstation” may be used in reference tospecifically either the data or voice capability at the agent'sposition, as appropriate to the context. For example, “routing the callto the agent's workstation” means routing a call to one of the voicedevices 161 a-161 c at the agent's position. Similarly, “routing thecall to the agent” means routing a call to the appropriate equipment atan agent's position.

The voice device used by an agent may be a soft phone device exemplifiedby a headset 161 a connected to the computer 160 a. The soft phone maybe a virtual telephone implemented in part by an application programexecuting in a computer. The phone may also comprise an InternetProtocol (“IP”) based headset 161 b or a conventional phone 161 c. Useof the term “phone” is intended to encompass all these types of voicedevices used by an agent, unless indicated otherwise. In someembodiments, the voice traffic to the soft phone may be transmittedusing the same facilities 168 used to convey data to the agent'sworkstation computer. In other embodiments, voice may be conveyed onseparate facilities 165.

After completing a call, the dialer 155 may generate call record datathat is stored in the data store 175 and the data store may include adatabase. The call record data indicates the progress and status of thecall. The call record data may indicate the time the call wasoriginated, the number dialed, the call disposition, when the call wasanswered, whether an answering machine was encountered, etc. In someembodiments, call recording of the audio data of the call may also bestored in the data store 175. The audio of the call may be analyzed by aspeech analytics system to ensure that the agents properly handled thecall and followed the appropriate procedures, and can be used toevaluate agent performance.

The contact center may also incorporate a private branch exchange(“PBX”) 135. This may be embodied as a TDM or VoIP based switchingdevice for handling voice calls as well as incorporating othercapabilities. Other embodiments may use a private automatic branchexchange (“PABX”), Internet-Protocol-PBX (“IP-PBX”), or other switchingdevice. The term “PBX” as used herein is intended to encompass thesevariations. The PBX 135 may allow agents to use their phones 161 a-161 cto originate and/or receive calls to other agents using facilities 165or 168, as well as originate or receive “outside” calls via facilities123 to the PSTN or facilities 116 h, local network 170, and 116 f to theInternet 123 b. Various topologies and configurations are possible as tohow the PBX may provide access. Specifically, an agent may dial a numberto place a call (such as to a wireless device 110 c) using aconventional, VoIP, or ISDN phone 161 a-c using facility 165 via PBX135. In some embodiments, the agent may dial the number to place thecall via phone 161 a using facilities 168 and 116 h via the PBX.

Normally, agents may communicate using a phone with either a PBX or adialer in a contact center, but not both. The PBX and dialer aretypically configured so that each can complete their respective callprocessing functions (for either incoming or outgoing calls as may beappropriate) in a stand-alone configuration, without requiringcooperation with each other to complete a call.

In addition, the contact center may incorporate a compliance server 125.The compliance server 125 may connect via facilities 116 i to the localnetwork 170, which in turn may provide access to facilities 165 tophones as well as facilities 168 for voice and data, depending on thecontact center configuration. The compliance server may have facilities127 to the PBX, the role of which is discussed further below. In someembodiments, the compliance server 125 may be a modified dialer orincorporate aspects of a dialer, with respect to accomplishingcompliance enforcement.

The architecture shown in FIG. 1 illustrates one possibility, and doesnot limit application of other architectures of the principles andtechnologies presented herein. Further, not all aspects and componentsshown in FIG. 1 are required in all embodiments. Thus, a contact centermay have agent positions using only a workstation configuration 160 a,161 a involving soft phones, whereas other contact centers may use otherconfigurations. In some configurations, the phones may be capable ofhandling two lines, and may have the capability of handling a dialeroriginated call on one line and a manually originated call via the PBXon another line. Those skilled in art will recognize FIG. 1 representsone possible configuration of a contact center architecture 100, andthat variations are possible with respect to the protocols,configurations, facilities, technologies, and equipment used.

The above components may be variously referred to as a “computer,”“processing device,” “unit,” “component,” or “system” and mayincorporate therein a local data store or database, or interface with anexternal database. Use of the word “server” herein does not require thecomponent to interact in a client-server arrangement using web-basedprotocols with other components, although that may be the case. Further,the above components may be located remotely from (or co-located with)other components. Furthermore, one or more of the components may beimplemented on a single processing device or platform to perform thefunctions described herein.

In addition, the contact center architecture 100 may be provided as ahosted solution, where the call processing functionality is provided asa communication service (a so-called “communication-as-a-service” or“CaaS”) to a contact center operator. Thus, there is no requirement thatthe components identified above must be actually located or controlledby a contact center operator.

In addition, the agent positions can be co-located in a single physicalcontact center or in multiple physical contact centers. The agents canbe remotely located from the other components of the contact center, andmay also be remotely located from each other, sometimes referred to as a“virtual contact center.” A virtual contact center may describe ascenario where agents work at home, using their own computers andtelephones as workstations. In some configurations, a single physicallocation of the contact center may not be readily identifiable. This mayoccur when the call processing functions are provided as a service in ahosted cloud computing environment and the agent positions are in theirindividual residences.

A simplified description of the architecture of the contact center as itrelates to using the compliance server 125 and the PBX 135 is shown inthe system 200 of FIG. 2. In FIG. 2 the agent's workstation comprisesthe phone 161, which is a softphone, and a computer 160. The computer isused to provide information to the agent relating to the account thatthe agent will dial. The computer may have a communications channel 132to the compliance server 125 for receiving such data and anothercommunications channel 134 to the PBX 135 used for the wireless callorigination. This configuration may vary in other embodiments. Further,the communications channels 134, 132 may represent different physical orlogical channels in different embodiments.

The PBX 135 is connected to the PSTN 115, via facilities 123 which isturn is able to route calls to wireless numbers associated with a mobilephone 110 c or calls to wireline numbers associated with a conventionaltelephone 110 b. Although the PBX can be used to originate calls towireline numbers, the illustrations herein largely focus on originatingcalls to wireless numbers. The compliance server 125 is illustrated ashaving facilities 121 to the PSTN. This can be used to originate othercalls to wireline numbers or receiving incoming calls. In someembodiments, the compliance server does not have any facilities 121 forconveying voice traffic to the PSTN 115, or the Internet. Again, sincethe illustrations herein largely focus on originating calls by the PBXto wireless numbers, the communication facility 121 is not required inall embodiments. The compliance server 125 may interconnected with thePBX 135 via facilities 127. This may be a signaling link, a voicecommunication facility, or a combination of the two.

EMBODIMENTS

Various embodiments are possible to provide compliance enforcement formanually dialed calls to wireless numbers. The embodiments generallyinvolve cooperation between the compliance server 125 and a PBX 135.Although shown as two separate devices in FIG. 2, these two componentscan be integrated into one device in some embodiments. The complianceserver 125 may incorporate certain aspects of a predictive dialer, aspredictive dialers are typically used to enforce compliance whenoriginating calls. In the embodiments disclosed herein, the complianceserver enforces compliance for calls to wireless numbers, but does notoriginate the wireless call. The PBX 135 (or other similar form ofswitching device) originates calls to the wireless numbers that aredialed by the agent using the phone at the agent's position. Note thatin some embodiments, the compliance server 125 receives and processesvoice data from the PBX 135, as the compliance server may be involved inrecording or processing of audio data associated with the wireless call.The audio data may be stored and/or relayed to a data store by thecompliance server. Thus, although the compliance server may notoriginate voice calls, it does not necessarily exclude the complianceserver from receiving and processing voice and audio data.

Embodiment One

This approach incorporates the PBX 135 for originating calls to awireless number that is manually dialed under the control of the agentusing the phone 161. Although the embodiments herein are illustratedusing a PBX, other switching elements can be used, including, but notlimited to: an IP-PBX, optical switch, voice switch, router, PABX,session border controller, MPLS switch, etc. In short, the principlesand technologies can be applied to any device capable of switching voicedata. The PBX 135 cooperates with the compliance server by bridging(a.k.a. conferencing) the compliance server 125 onto the call originatedby the PBX 135. All dialing is manually under the control of the agentinteracting with the PBX 135, and the storage of the numbers to bedialed is in the compliance server 125, which is separate from the PBX.The compliance server is able to maintain status information about thecall and/or agent, to ensure that regulations are complied with.

Turning to FIG. 3, a messaging diagram 300 shows the message flow thatoccurs between various components, namely the agent's computer 160 andphone 161, the PBX 135, the compliance server 125, and the PSTN 115. Thecomputer 160 and phone 161 are co-located at the agent's workstation orwork position and are both operated and controlled by the agent.Although the phone may be a soft phone, the principles apply to using aVoIP or conventional phone.

The PBX 135 is a well known device for originating calls that aremanually dialed under the direction of the agent. It is presumed thatthe PBX does not meet the “autodialer” requirements as considered by theFCC rules. Specifically, the PBX does not (or is not configured to)generate or store the number manually dialed by the agent as defined inthe context of the TCPA. Rather, the agent manually enters the digits ofthe wireless number using the phone 161 that will cause the PBX tooriginate a call to that number. Any number of approaches for the phonesignaling to the PBX may be used.

The compliance server 125 may be a computing system as is well known inthe art. It may incorporate aspects of a dialer, particularly thecompliance enforcement functions found in certain commercially availabledialers, such as the Noble Systems Corporation Maestro™ predictivedialer. The compliance server is typically not used to originate callsto wireless numbers.

Finally, the PSTN 115 is shown to convey the call originated by the PBXto the called party. In other embodiments, the Internet or other form ofnetwork may be used. Reference to the PSTN should not be construed tolimit any of the technologies used herein from using VoIP, SIP, or otherforms of digital telephony.

The process begins with the agent using their computer 160 to log-on tothe compliance server at operation 320. This process indicates to thecompliance server 125 that the agent is available to handle calls, andallows the compliance server 125 to perform various functions associatedwith an agent logging on. The compliance server 125 knows which agentphone extension is associated with the agent, what skill level the agenthas, schedule, what campaigns the agent may participate in, etc. As aresult, the compliance server 125 updates the agent's status and addsthe agent to the pool of available agents for handling calls.

Next, the compliance server 125 may activate a trigger on the PBX 135associated with the agent's dialing plan via signaling at operation 322.The trigger is a process in the PBX that is involved when processingcall origination requests from the agent. In other words, this defineshow the call origination for that agent's phone is to be handled by thePBX. When activated, the PBX will automatically establish a conferencecall involving the compliance server. The signaling at operations 322and 324 are optional, in that some embodiments may provision the triggerin the PBX permanently for the agent's phone. However, in thisembodiment, the trigger for the agent's phone is only activated when thecompliance server 125 determines that the agent will be engaged in acampaign involving manually dialing wireless numbers. Otherwise, the PBXmay interpret call setup from the agent's phone in a conventionalmanner.

The PBX may confirm back to the compliance server 125 that triggeringfor the agent's phone will occur at operation 324. At this point, thecompliance server 125 may update the status associated with the agentand/or call in operation 326, since the compliance server now knows theagent is ready to originate calls.

As it will be seen, the compliance server is able to track and updatethe status of the agent and/or call throughout the various stepsencountered by the agent/call. Although the compliance server does notoriginate the call to the wireless number, the compliance server istimely notified in various ways so that it is able to maintain currentstatus information in a largely comparable manner as if it hadoriginated the call.

The compliance server 125 at this point may update the appropriatestatus or state for the agent to reflect the operational status of theagent's phone and/or computer. The compliance server 125 may include theagent in internal queues for handling calls associated with thecampaign. In this embodiment, it is presumed that the agent is engagedin a campaign that involves initiating calls to wireless numbers. Thecampaign may involve a list solely comprising wireless numbers or mayinvolve a mix of wireless/wireline numbers. Once the compliance server125 determines the agent is ready to originate a call, the complianceserver 125 sends information at operation 328 to the screen of theagent's computer 160 indicating one or more numbers to dial.

The presentation on the agent's computer of what number(s) that shouldbe dialed may be presented to the agent in various formats. Theinformation may include the number, as well as other related accountinformation. In one embodiment, a plurality of numbers is presented in agrid format. This provides numbers on a variety of accounts, where eachaccount may have multiple numbers associated with that account. Thisallows the agent to determine which of several numbers they will dialnext. The grid may be a series of rows with fields for account number,account holder name, amount due, address, and notes. In otherembodiments, a single wireless number, along with account information,may be provided to the agent. A variety of graphical user interfaceformats may be presented in which the agent is informed of a wirelessnumber to dial. In various embodiments, the graphical user interfacepresented may mimic the same format used to dial wireline numbers by apredicative dialer.

The compliance server may select or identify the number(s) that theagent may select from to dial. In one embodiment, the compliance serverhas already performed the necessary compliance processing beforepresenting the numbers to the agent to select from. Doing so ensuresthat only allowable or compliant numbers are presented to the agent todial. In other embodiments, the compliance server may perform complianceenforcement at a later stage (see processing operation 334 below).

After receiving a message at operation 328, the agent reviews theaccount information on their computer screen. It is presumed that ifmultiple accounts and/or telephone numbers are presented, that at leastone number is a wireless number and that information is conveyed to theagent indicating it is a wireless number. Of course, if the entire listcomprises wireless numbers, then the agent may be informed at thebeginning when reviewing the list or otherwise understand that allnumbers are wireless numbers.

The agent may then manually dial the wireless number presented on thecomputer screen using the phone that is connected to the PBX 135. Thisis represented by the signaling at operation 330 in FIG. 3. Based on thephone technology used by the agent, there may be a series of distinctinputs by the agents as they individually press a key or screen iconindicating a dialed digit of the called telephone number. Forsimplicity, a single message at operation 330 is shown.

Different phone technologies may be used by the agent. The phone may bean analog phone in which the agent presses physical keys on the phone togenerate dual-tone multiple frequency (“DTMF”) tones. The phone may be aphysically distinct VoIP phone or an ISDN based telephone, also having akeypad. In this case, the agent pressing a key may result in SIP or ISDNsignaling when sending the one or more messages at operation 330. Inother embodiments, in-band DTMF tones, proprietary station setsignaling, or other forms of signaling may be used. The phone could be asoft phone that is integrated with the computer and interfaces with thePBX using any of the above signaling protocols. In one embodiment, thedigit keys may be icons on the computer screen that are selected by theagent or the keys may be indicated using the numerical keypad on theagent's computer keyboard. Depending on the soft phone embodiment,various human interface interactions may occur for the agent to dial thewireless number. For example, the agent may use a mouse, a pointer, atouch screen, a separate keypad interfacing to the computer, speechrecognition, etc.

Depending on the phone technology used, the agent may hear in-bandtones. In some embodiments, the agent may hear a dial tone and DTMFtones, which may occur if a conventional phone is being used. In otherembodiments, such as when using a VoIP phone, “comfort tones” may beprovided to the agent to emulate a dial tone and DTMF tones, even thoughthe signaling of the wireless number is conveyed via out of banmessages. Thus, the agent may be provided such tones in operation 333.Whether and how this occurs is defined according to the dialingprocedures associated with the agent's phone and the PBX.

Upon receiving the wireless number to dial, the PBX 135 processes thereceived digits, and then may transmit a query to the compliance server125 at operation 332. The query essentially asks the compliance serverwhether it is okay for the PBX to dial the call. Or, in other words,have the appropriate compliance requirements have been met? The querytypically includes the number dialed by the agent, as well as thestation ID and/or agent ID. Other information may be included in thequery. The query can be structured according to a number of availableprotocols known by those skilled in the art, including any of theInternet-related protocols, telephony-based protocols, proprietaryprotocols, including H.323 protocols. Inter-Asterisk Exchange Protocol(“IAX”), etc. In some embodiments, the query is optional as thecompliance server can confirm or deny authorization for the call toproceed upon receipt of a call leg from the PBX (see below).

In one embodiment, the PBX is not aware of the various compliancerequirements, nor does the PBX store the dialing list including thewireless number, nor produce the wireless number to the agent. Thus, thePBX may not know if the number was just dialed by another agent, but thecompliance server may know. Consequently, the PBX relies upon thecompliance server to perform the compliance processing and hence asksthe compliance server whether the number can be dialed.

If the compliance server 125 has not already done so, the complianceserver 125 applies the various compliance processing rules in operation334 to determine whether the applicable compliance requirements havebeen meet. The requirements may be dependent on various aspects,including contact center policies, context/purpose of the call,government regulations, etc. The compliance server 125 further updatesthe status information associated with the agent and/or call.Specifically, the compliance server 125 now knows that the agent hasinitiated a call request and knows the number dialed, as well as thelist of numbers presented to the agent from which the number wasselected. The compliance server may verify that the number dialed by theagent is one of the numbers just presented to the agent. Assuming thatall the applicable compliance processing rules have been applied and thecompliance server has determined that the call may proceed, thecompliance server confirms to the PBX that the call may proceed via amessage at operation 336. An error or non-compliant condition mayinstead result in signaling at operation 336 indicating to the PBX thatthe call should not be established or indicate the error condition.

The compliance server may update status information associated with thecall/agent in operation 338. For example, the compliance server nowknows that the agent has manually dialed a wireless number via the PBX,and the PBX is in the process of handling the call.

After receiving the response 336, the PBX proceeds by establishing a3-way call (i.e., a conference call) using a conference bridge 340wherein a first call leg 342 is established to the compliance server125. This again can be accomplished using any well known protocol suchas session initiated protocol (“SIP”), integrated services digitalnetwork (“ISDN”), H.323, etc. After the compliance server confirms tothe PBX that the call may proceed at operation 336, the complianceserver may start a timer in expectation of receiving the incoming callleg 342 from the PBX. In one embodiment, information is conveyed in theANI (calling party number) or DNIS (called party number) of the call leg342 that may indicate the wireless number dialed by the agent, to allowthe compliance server to associate the call leg 342 with the agent, andthe number selected by the agent. Other signaling mechanisms could beused in other embodiments. The expiry of the timer indicates anexceptional condition, such as abandonment of the entire process or afailure of the PBX. Once the compliance server receives the incomingcall leg 342, the compliance server will update the status associatedwith the agent in operation 345.

Although not shown in FIG. 3, the compliance server may further bridgethe call leg 342 with a recording system (not shown) that may involvesanother call leg originating from the compliance server. In otherembodiments, the recording of the call may involve the compliance servermerely copying the audio data to a file or data store.

Co-incident with this process, the PBX also establishes an audio path344 to the phone of the agent. This could be considered another call legof the conference call. The details on how this is performed vary as tothe type of phone used by the agent. For example, the phone used may bean analog phone, a digital phone (non-VoIP), a digital VoIP phone, or asoft phone that is integrated into the computer. In each case, the phoneis logically distinct from the computer, even if integrated into thecomputer. Appropriate signaling and procedures are based on the type ofphone and are well known. In some embodiments, this audio path may beinitially established for the first wireless call and maintained untilthe agent logs out.

Next, the PBX establishes another call leg 348 to the dialed party. Thismay occur using various types of signaling, such as POTS, ISDN, SIP,etc. The PBX may also provide, optionally, the aforementioned in-bandcomfort tones 346 to the agent to inform the agent of the progress ofthe call. The provision and form of the tones may vary based on thetechnology, including the particular form of telephone used by the PBX.For example, the PBX may be a VoIP-based platform, so that there is noin-band tones produced to the agent's phone as is found in a POTSsystem. In other embodiments, the PBX may generate a dial tone and DTMFtones as the call leg 348 to the dialed party is established mimickingthe POTS operation. In some embodiments, the DTMF tones are not thebasis for actually conveying address information between the PBX and thetelephone network, as that information may be conveyed by other forms ofout-of-band signaling, including SIP, ISDN, or MF. However, in otherembodiments, the PBX may be a TDM-based system that does actuallyprovide and use DTMF for conveying dialed digits. It should berecognized that a wide variety of arrangements are possible forproviding tones to the agent to reflect the manually dialed wirelessnumber.

Once the dialed party answers the call leg 348, a three-way orconference call is established between the agent, the called party, andthe compliance server. The compliance server is largely “listening” andmay not provide any audio to the conference. The compliance server mayperform recording, quality analytics, speech analytics, etc, similar toas if a predictive dialer had originated the call. For example, thecompliance server may monitor any in-band tones or signals provided bythe PSTN or remote party, such as a busy signal, answering machinegreeting, or other special information tone (“SIT tone”). The SIT tonecan indicate whether a number is disconnected, ported, etc. This allowsthe compliance server to properly record the status of the call (i.e.,disposition the call), as opposed to the agent manually entering thestatus or disposition code. Thus, the compliance server may haveexposure to all of the audio data associated with the call in order toperform the complete suite of compliance enforcement functions.

It should be appreciated that in this arrangement, the agent hasinitiated the call via the PBX, not the compliance server. Further,although the compliance server may have indicated to the agent one ormore wireless numbers to be dialed, the agent selected the number andmanually dialed the wireless number using the PBX, in a similar mannerto that which the agent would use to perform any other manually dialedcall using the PBX. Further, the PBX does not store, produce, or accessa database for originating the call to the wireless user.

It should also be appreciated that the above steps may vary in differentembodiments. Specifically, the call leg to the agent, the call leg tothe compliance server, and the call leg to the called party may bevariously established serially, in parallel, or in combination. In someembodiments, the audio path to the agent may be maintained betweencalls. In other embodiments, the audio path to the compliance server maybe maintained, and other signaling approaches are used to convey thedialed number to the compliance server. No doubt those skilled in theart can develop other variations for coordinating the compliance serverand the PBX upon reading this disclosure.

Once the agent has completed their interaction with the called party,the three-way call is terminated. This can occur in various ways. Theapproach shown in FIG. 3 illustrates the agent indicating a dispositioncode for the call using their computer. The disposition code indicatesthe status of the call, such as whether the right party was reached, anissue was resolved, a sale completed, etc. In some cases the agent isexpected to indicate the disposition (a.k.a. dispositioning the call).This is typically required when the agent has spoken with an answeringparty, since the code depends on the substance of the conversation. Insome instances, the compliance server can disposition the call. Forexample, the compliance server can listen to in-band call progress tonesand indicate whether the call encountered busy, no-answer, a disconnecttone, or was answered by an answering machine. Allowing the complianceserver to disposition the call in such cases relieves the agent fromhaving to do so, and often results in a more accurate disposition of thecall.

The computer will convey the disposition code to the compliance serverat operation 350. In response, the compliance server updates the agent'sstatus in operation 352. At this point, the compliance server knows thatthe call is over and releases the call leg 354 to the PBX. In response,the PBX also then removes the audio path 356 to the agent or otherwiserelease that call leg to the agent's phone. Again, the specific detailsof this process depend on the type of phone being used. Finally, the PBXreleases the call leg to the party at operation 358.

The operation of the 3-way bridge may be slightly modified from theoperation of a conventional 3-way bridge. In a conventional 3-waybridge, if an added leg to a conference is dropped, the conferencebridge may remain intact (e.g., the other remaining call legs areretained). However, in this embodiment, the 3-way bridge operates suchthat if any call leg is dropped, the remaining call legs are alsodropped. This is because the compliance server is bridged to the callbetween the agent and the remote party to only listen to that call. Thisallows the compliance server to perform any of the various recording andanalytic functions mentioned above. The compliance server only drops itscall leg to the PBX if the agent dispositions the call, e.g., indicatesthe call is completed. The compliance server is configured so that whenthe agent dispositions the call, the compliance server construes thisaction as the agent having completed the call with the called party andinitiates releasing the call leg. The agent could have alternativelyreleased the call to the called party (i.e., to the PBX) and thendisposition the call to the compliance server.

If the called party terminates their call leg, then there is no need forthe agent to be bridged to the compliance server, and again there is noneed to keep the bridge up. Similarly, if the agent terminates theircall leg first, then call leg to the called party should be terminated.At that point, there is no need for the call leg to the complianceserver, so it is released as well.

As evident, there are a number of alternatives possible in the messageflows shown above. The exact sequent of events that occur when the 3-waycall is established can vary from what is shown, and there are variousalternatives for releasing the three-way call. Other variations exist asto when certain compliance operations are performed, how the outcome ofthe compliance testing is indicated to the PBX, and how other operationsare performed. FIG. 3 is not intended to limit the potential ways thatthe overall system may operate.

For example, as shown in FIG. 3, the coordination between the PBX andthe compliance server is manifested via a query 332 and response 336.The query could be implicit when the PBX establishes the call leg 342 tothe compliance server. In such embodiments, there may not be anexplicit, stand alone query 332. In some embodiments, the calling partytelephone number used by the PBX in the call to the compliance servercould be the same value as the wireless number. This allows the call legto be correlated with a particular wireless number in the complianceserver. The compliance server then responds by accepting the call leg orrejecting the call leg as indications that the call can proceed or not.In some embodiments, this information may be conveyed byuser-user-information (“UUI”) in ISDN messages. In other embodiments,the PBX may not bridge on the compliance server via a three way call.However, not bridging the compliance server prevents the complianceserver from performing certain functions, such as call recording,monitoring call progress tones, etc.

Also, it is evident that the compliance server is able to maintaincurrent status information about the agent and/or call based on agentinteractions with the compliance server via the computer, as well asupdates from the PBX, and by monitoring in-band tones as the callprogresses. These inputs allow the compliance server to know therelative state of the agent and/or the call and when the agent is readyto initiate another call. The compliance server also knows whattelephone numbers the agent enters to the PBX. Thus, although thecompliance server is not originating or controlling call establishment,it is able to effectively monitor the call progress as if it hadoriginated the call.

Once the 3-way bridge is released, the entire process may loop back 360and repeat. The compliance server may present the agent with a new listof wireless numbers that may be dialed, and the agent can select thedesired number and originate another call. The compliance server mayupdate its records as to which numbers were dialed and may ensure thatthe new numbers presented to the agent do not result in complianceviolations if dialed. The compliance server can ensure that the agentcompletes a disposition code before additional numbers are presented tothe agent, or before another call is allowed to proceed if dialed by theagent. The compliance server is able to maintain statistics of how longthe agent was on the call, duration between calls, number of callsoriginated per time period, status of the originated calls, etc. Inshort, virtually any performance metric that is regularly maintained bya conventional predictive dialer can be applied, used, and maintained bythe compliance server.

At each step of the process, the agent is controlling the callestablishment by selecting the number to be dialed, entering the dialednumber, and listening to the call progress tones generated by the PBXwhen generating the call. Further, the PBX is not originating the callautomatically, nor is the PBX dialing a number from a database.

Blended Operation

Blended operation refers to a contact center handling both incoming andoutgoing calls. Blended operation may provide a benefit of allowingagents to originate outgoing calls when there are few incoming calls. Inmany embodiments, the incoming calls are handled by an automatic calldistributor (“ACD”) that may be a stand-alone device, or integrated withthe PBX or the compliance server. The ACD may offer the call to theagent using a separate phone. Thus, in some embodiments the agent mayhave two phones, e.g., a physical VoIP phone distinct from theircomputer for originating calls via the PBX to wireless numbers, and asoft phone integrated into their computer for handling incoming calls.In other embodiments, the agent may have a phone capable of handling twolines (either physical or logical). For example, the agent may have asoft phone which is able to receive incoming calls from the ACD on oneVoIP channel and originate outgoing calls to the PBX using another VoIPchannel. In other embodiments, the agent may have one phone capable ofonly handling one call, and this effectively prevents the agent fromoriginating an outgoing call at the same time.

Wireline Call Origination

The compliance server may be based on modifying a predictive dialer sothat it does not originate calls. However, in other embodiments, thecompliance server may function as both a compliance server for wirelesscalls originated by the PBX, and a predictive dialer for originatingcalls to wireline numbers. In this case, the same or different phone atthe agent's work space may be used for predictive dialer originatedcalls. In some embodiments, a dialing list may comprise both wirelineand wireless numbers, and the processing of numbers on that list mayinvolve a single agent handling wireline predictive dialing calls andwireless manual dialing calls. Thus, returning to FIG. 2, the complianceserver 125 may be integrated with a predictive dialer that dialswireline numbers via facilities 121. In this case, the predictive dialerdials wireline numbers and performs compliance functions. When wirelessnumbers are dialed, the compliance server performs the compliancefunctions, and the PBX originates the wireless calls.

In other embodiments, originating calls to both wireline and wirelessnumbers can be accomplished by using a compliance server and PBX asdescribed herein for originating wireless calls and a predictive dialerfor wireline calls. To accomplish this, segregated lists of wireline andwireless numbers need to be prepared, loaded and managed for thepredictive dialer and the compliance server respectively.

Process Flow

A process flow corresponding to the message flow of FIG. 3 is shown inFIGS. 4A and 4B. Turning to FIG. 4A, the process 400 begins with thecompliance server receiving the agent's log-on in operation 404. Thecompliance server retrieves the agent's profile information in operation406, and performs related operations, such as updating the status toreflect the agent is available to handle calls.

The compliance server may inform the PBX that the dialing planprocedures for the agent are to be activated in operation 408. Thisoperation is optional, and may not occur in every embodiment. Next, thecompliance server presents to the agent the wireless number(s) that maybe dialed in operation 410. This may mimic the screen layouts used fordialing wireline numbers by a predictive dialer so that that agent seesthe number in a familiar screen. Additional icons may inform the agentthat the number is a wireless number that has to be dialed manually.

The compliance server receives the agent's selection of a number theywill be dialing indicated by the agent via a mouse or cursor inoperation 412. This operation is optional, as this provides an advanceindication to the compliance server as to the number selected by theagent. The agent may simply dial the number using their phone that issignaled to the PBX, at which point the PBX sends a query to thecompliance server. At operation 414, the compliance server receives thequery from the PBX.

The compliance server determines in operation 416 whether it is okay forthe PBX to originate the call to the number. The compliance server mayhave performed some compliance aspects previously, or may have waiteduntil this point to perform the compliance testing. If the call is notin conformance with the requirements, then in operation 418 thecompliance server denies the request.

Assuming that in operation 416 the call may be dialed, the complianceserver may confirm to the PBX that the call may proceed in operation420. The compliance server then updates the state information reflectingthat it expects an incoming call will be shortly received from the PBX.The call is then received from the PBX in operation 421. The processcontinues to label A 425 on FIG. 4B.

Turning to FIG. 4B, the incoming call may indicate via thecalling/called party number the wireless number dialed by the agent.This allows the compliance server to know that the incoming callcorrelates to the prior query. Other signaling mechanisms may be used. Acheck may be made in operation 422 to ensure that the query for theindicated wireless number matches the calling party number in the callsetup. If not, then in operation 424 an error message may be sent to thePBX. If the wireless number is not indicated in the incoming call, thenthis step may be skipped or may be accomplished in a different manner.

Assuming there is a match in operation 422, the compliance server maymonitor and/or record the call in operation 430. The compliance servermay monitor the call process tones, analyze the conversation, record thespeech, etc.

Once the agent completes the interaction with the called party, one ofseveral options may be pursued. In one option, the compliance serverreceives a disposition code in operation 432 from the agent. If so, thecompliance server then releases the call leg to the PBX in operation434. The process then returns to label B 450 in FIG. 4A.

Another option is that the remote party will have released their callleg to the PBX. If so, the PBX may then release the call leg to thecompliance server and the compliance server may receive an indication ofsuch in operation 436. The compliance server knows that the call iscompleted, and may prompt the agent in operation 438 to enter adisposition code for the call that just ended. When it is received inoperation 440, the compliance server then returns to the processingassociated with label B 450 in FIG. 4A.

If the agent does not enter a disposition code, the compliance servermay block the presentation of the next set of wireless numbers to theagent in operation 410, or reject a request from the PBX to establish acall for the agent in operation 416. Thus, the compliance server cantrack or shadow the status of the agent and the call as if thecompliance server were originating the call, and indirectly control theestablishment of further calls by the PBX.

Combined Wireless and Wireline Call Originations

In various embodiments, the compliance server may be configured to onlyoriginate calls to wireless numbers, or it may be configured to alsooriginate calls to wireline numbers. It may be configured to originatecalls to wireline numbers as described above, via manual dialing or in apredictive dialing mode.

If the compliance server 125 does predictively dial calls to wirelinenumbers using facilities 121, then the compliance server may function asa predictive dialer. In this case, the compliance server is accessing alist of numbers and dialing a call, but to a wireline number. If thelist contains a wireless number, it can indicate this to the agent withinstructions that the call is to be manually dialed. In this case, thecompliance server presents the wireless number to the agent, and theagent uses the phone to dial the call via the PBX, such that thecompliance server does not originate the wireless call in any way.

This embodiment also allows incoming calls to be handled. Returning toFIG. 2, the compliance server 125 can be integrated into an ACD thatalso receives incoming calls. As is well known for blended call centeroperations, when the agent is involved in an outgoing call, no incomingcalls are offer to that agent. That is, any incoming calls received areonly routed to the agent if the agent is not handling another call.

Embodiment Two

This embodiment also involves a PBX interacting with a complianceserver. This embodiment is based on the compliance server originating athree-way call to the PBX, as opposed to the PBX originating a three-waycall to the compliance server. The compliance server is able to monitorand record the call, but dialing of the call originates from the agentand is directed to the PBX with the dialed digits handled by thecompliance server in some embodiments.

In one embodiment, the compliance server may incorporate aspects ofpreview dialing in presenting the number to the agent to dial. Previewdialing selects one or more account records and presents variousinformation on the account record(s) to the agent for review. Thus, theagent can “preview” the information before the call is originated. Theagent can select a record and then control when the call is originatedby selecting a screen icon, pressing a key, or some other form of input.The telephone number associated with the record is then dialed. In oneembodiment, the compliance server may then provide the digits to the PBXto dial.

The modifications ensure that the call is established by the agentinteracting with the PBX, and that the PBX does not store, produce orotherwise access a database of numbers when originating the call. Recallthat in Embodiment One, the agent's phone is connected to the PBX, andthe PBX creates a three-way call to the compliance server, allowing thecompliance server to receive audio and process and/or record audio dataas necessary. In this embodiment, the compliance server creates thethree-way call.

Referring back to FIG. 2, in Embodiment Two, the agent's phone 161 maybe connected to the compliance server 125 via facility 132, and thecompliance server bridges or connects a call leg to the PBX usingfacility 127. If the compliance server needs to add on a recordingsystem to record the audio, then a bridge may be required in thecompliance server to bridge a call leg to an external recording system.If the compliance server does not need to connect to an externalrecording system, than a bridge may not be required. In this case, thefacility 132 to the agent's phone is connected to the PBX via facility127. In one embodiment, the agent's phone 161 generates the DTMF tones(or these may be generated by a tone generator in the computer 160responsive to the phone 161) representing the wireless number. Theinformation is conveyed over facility 132, through the compliance serverand over facility 127 to the PBX 135, and the PBX originates the call asin the earlier embodiment. In other embodiments, the phone may passsignaling information (e.g., SIP or ISDN signaling messages) as opposedto in-band tones to the compliance server 125 that, in turn, relays thesignaling to the PBX or passes it through to the compliance server suchthat the signaling is processed by the PBX.

In other embodiments, the agent may request the compliance server sendthe number to be dialed to the PBX, and the compliance server thenconnects the agent to the PBX. In this last embodiment, the phone doesnot send the wireless number over the facility 132. In each of theseembodiments, the compliance server retains its functionality of ensuringcompliance is enforced and that the PBX originates the calls.

A message flow 500 of this embodiment is shown in FIG. 5. The processbegins in operation 520 with the agent logging into the complianceserver 125 using their computer 160. In some embodiments, additionalmessaging may follow where the compliance server activatesagent-specific functionality in the PBX, but these messages are notshown in this embodiment. The compliance server is able to then updatethe agent's status in operation 526. Next, the compliance servertransmits to the agent's computer the next wireless number(s) that areto be dialed in operation 528. After reviewing the number(s) and relatedaccount information, the agent enters the number to be dialed via theirphone 161 in operation 530.

The agent can indicate the number to dial by manually dialing the digitsor by selecting a number in conjunction with a preview capability. Thecompliance server then establishes a three-way bridge 532 that connectsthe agent to a recording system 505 at operation 531, and the PBX 135 atoperation 534. The recording system is shown as a separate entity inFIG. 5 in order to illustrate various options.

The manner in which the call leg between the compliance server and thePBX is established may vary. In one embodiment, the compliance serverhotlines (automatically connects) the call leg to the PBX. Thecompliance server effectively connects the call leg to the agent's phoneto the call leg to the PBX. Thereafter, the PBX may provide audio tonesand receive the dialed digits from the agent. Although these in-bandtones or out-of-band signaling messages may be relayed by and throughthe compliance server, the compliance server is not establishing thecall.

In another embodiment, when the agent selects the number to dial atoperation 530, the compliance server connects to the PBX and sends thedigits to the PBX. In this case, the digits to be dialed are conveyed bythe compliance server to the PBX, but the call origination is performedby the PBX.

The PBX connects in operation 536 the call leg from the complianceserver with the call leg established for the originating wireless callleg in operation 538. Alternatively, the originating wireless call legin operation 538 can be established and then connected to the call legbetween the PBX and compliance server. In any case, a connection isestablished from the agent, to the compliance server, back to the PBX,and then out to the PSTN 115 and the called party. The compliance serveris aware that the call has been established and then updates the agentstatus information in operation 545. As before, the compliance server isable to monitor and record the audio associated with the call progressas well as any conversation.

When the agent is finished talking with the called party, the agentdispositions the call by signaling the disposition code to thecompliance server at operation 550. The compliance server updates theagent status as appropriate in operation 552 and then may release thecall leg back to the PBX in operation 554. The compliance server mayalso release the call leg to the agent in operation 556. The PBX, inresponse to the call leg released in operation 554, releases the callleg to the called party in operation 558. The process may loop back inoperation 560 and repeat as necessary.

Process Flow

The process flow corresponding to the message flows of FIG. 5 is shownin FIG. 6. This embodiment presumes that a single list comprising bothwireline and wireless numbers is processed by the compliance server. Inother embodiments, different lists may exist, one for wireline and onefor wireless. In the case where the list only comprises wirelessnumbers, the process flow may be slightly different from that shown inFIG. 6. Specifically, operations 625 and 630 may be absent.

The process 600 begins in operation 605 with the compliance serverretrieving the next set of telephone numbers in the dialing list forpotential dialing. In this embodiment, a group of records are retrieved;however, in other embodiments, only a single record may be retrieved.This operation may be the point of re-entry when repeating the overallprocess.

Next, the compliance server displays the retrieved records on thecomputer of the agent in operation 615. A number of graphical userinterface formats may be used to present the information, which mayinclude other account information associated with the telephonenumber(s). Presumably, if the numbers are of either a wireless orwireline type, an indication of each type of number is provided to theagent. This operation allows the agent to determine which number fromthe various accounts is to be dialed next. The compliance server mayhave performed various compliance processing prior to displaying therecords to the agent. That is, in one embodiment the fact that thenumber is presented to the agent by the compliance server means that thenumber is eligible to be dialed, if so chosen by the agent. In otherembodiments, the number displayed is not checked for compliance untilthe agent identifies the number that the agent would like to dial.

The agent selects one of the telephone numbers presented by thecompliance service and the compliance server receives the selectednumber in operation 620. The agent may identify their selection by usinga pointing device, mouse, touch screen, keyboard, etc. The selectioncould be identifying the numbers individually or selecting the number asa whole.

The next operation is a test, which presumes that the list incorporatesboth wireless and wireline numbers. If the list only comprises wirelessnumbers, then this test would not be required. The test in operation 625determines if the selected number is a wireless number. If not (e.g., awireline number), then the compliance server may function as a previewdialer and originate the call. In many embodiments, the list will onlycontain wireless numbers since it further avoids dialing wirelinenumbers in a manual manner similar to wireless numbers. Thus, in someembodiments, the dialing list is not integrated with wireline andwireless numbers, since inefficiencies are introduced when dialingwireline numbers individually.

If the number is a wireless number in operation 625, then the complianceserver establishes a connection between the agent's phone and the PBXusing the facility 127 between the PBX 125 and compliance server 135.This facility could be analogous to a tie trunk between the two, whichis a permanent connection for voice, or a data connection. The agent'sphone is connected to the compliance server, and connects the agent tothe PBX. In one embodiment, the agent is connected to a tone receiver inthe PBX. In this case, the agent may dial the wireless number to thePBX, although the information may be relayed through the complianceserver. In another embodiment, the compliance server may transmit thedialed digits to the PBX. A bridge may be present in the complianceserver so as to monitor and record the progress of the call.

For purposes of illustration, it is presumed that the compliance serverconnects the agent to the PBX that then allows the agent to originatethe call by the PBX. In operation 635, the facility 127 is used toconnect the agent to the PBX. Next, the PBX may provide dial tone backto the agent's phone in operation 640. The agent, in response, manuallydials the number displayed on the computer screen using the appropriateman-machine interface provided according to the type of phone inoperation 645, which are received by the PBX. In some embodiments, thismay be a soft phone and the agent may use the numeric keypad on thecomputer keyboard to enter the wireless telephone number. Depending onthe embodiment, the agent may enter a “return,” “enter,” or “send” tosignify the end of the digits. In other embodiments, the PBX may employtimers or digits counters. In one embodiment, DTMF tones are generatedby the soft phone to indicate the digits pressed by the agent. In otherembodiments, the soft phone may originate SIP signaling which isconveyed to the PBX.

At this point, the compliance server is maintaining a connection betweenthe agent soft phone and the PBX. Thus, the compliance server canmonitor the in-band information and determines the DTMF digits beingdialed by the agent to the PBX. In this manner, the compliance server isable to monitor the status of the call and any audio data beingconveyed. Further, the agent's phone is interacting with the PBX fororiginating a call, not the compliance server.

The PBX originates the call in operation 650 in a conventional manner.After conversing with the called party, the agent may then terminate thecall in operation 655 (or the called party may terminate the call). Thecompliance server may not know that the call is terminated. However, theagent then dispositions the call by indicating the appropriatedisposition code using the workstation computer in operation 660. Thecompliance server, by receiving the disposition code, knows that thecall has ended, and can appropriately update the status of the accountand disconnect the agent's phone to the trunk. The PBX may then releaseany remaining call legs associated with the conference.

The compliance server is able to maintain status information for theagent and/or call in that the agent indicates the number selected. Thus,the compliance server knows to connect the agent's phone with the PBX.The compliance server is able to monitor the dialed number indicated byDTMF tones, and know that the called party is being dialed. Further, thecompliance server knows the call is over when the agent dispositions thecall. Thus, even though the compliance server is not processing ororiginating the call to the wireless number, it is aware of the generalstatus via the agent's indications. As with the previous embodiment, theagent originates calls to the PSTN via the PBX, not the complianceserver.

Maintaining Agent State Information

In both embodiments, the compliance server tracks the agent's status.“Agent status” covers various status information related to the agentand/or the call, including the status of their desktop space, theirlog-in status, their call origination status, call progress, calldisposition status, etc. It may include status about the agent asreflected by the computer as well as reflected by the wireless callprogress. In regard to the agent's workstation computer, the complianceserver knows when the agent is logged-in and ready to initiate anotherwireless call. The compliance server knows if one or more numbers havebeen presented to the agent for dialing, and whether the agent hasselected one for dialing. The compliance server is able to monitor theprogress of a call and determine whether it has been answered,encountered busy, disconnected, or answered by an answering machine.Further, the compliance server also knows if and when the agent hasdispositioned a call after the call is completed. The compliance serveralso knows if a call leg is released by the PBX. With this information,the compliance server knows when the agent is available to be presentedwith additional numbers to dial. For example, if the agent has not yetdispositioned a call that has completed, then the compliance server willprevent the agent from initiating another wireless call. If the agentattempts to do so, the compliance server can display appropriatemessages requesting them to disposition the previous call and can blockthe PBX from originating further calls.

With respect to the call originated by the agent, although thecompliance server does not originate the call, it is able to maintaincall state information about the status of the call. In someembodiments, the call state information is very precise. Specifically,in Embodiment One, the compliance server receives a request from thePBX, so that the compliance server knows that a call is attempted to aspecified destination. Further, the compliance server then receives acall leg from the PBX. This may be set up just before or just after thecall leg to the agent and/or the called party is established. Thecompliance server thus has an accurate perspective of when the call wasoriginated by the PBX, and may know by monitoring the in-band channelwhether the call was answered by a human, answering machine, or receivedintercept treatment. Similarly, in Embodiment Two, the compliance servercan also monitor in-band tones to maintain a precise and accurate statusof the call.

Because the compliance server is able to maintain information about boththe agent's actions with respect to the agent's workstation computer andthe call status, the compliance server is able to maintain detailedinformation about the agent's actions, work statistics, error handling,call progress, call statistics, and perform other aspects necessary tomonitor agent performance. The compliance server is also able to knowand update call establishment information to accurately ensurecompliance regulations are followed. For example, because the complianceserver knows whether a call originated by the agent encounters ano-answer condition, the compliance server is then able to ensure thatthe number is not re-dialed within a prohibited window. If thecompliance server was unable to ascertain the status of the callattempt, it would adversely impact the ability of the compliance serverto ensure calls were compliant.

Embodiment Three

The embodiments disclosed above are generally based on the architectureshown in FIG. 2. The architecture of FIG. 2 can be implemented usingco-located components, geographically separated components, or hostedcomponents provided whole or in part by a service provider.

Another embodiment is shown in FIG. 7. In FIG. 7, the architecture 700illustrates the mobile smart phone 110 c, which is shown asinterconnected to the PSTN 115, which in turn is connected viafacilities 123 to a PBX 135. In this embodiment, the PBX 135 comprises aswitch and control module 735 and a compliance module 725. The switchand control module 735 may be an open source switching fabric andcontrol software, or other form of switching and control capabilities.The switch and control module 735 is able to communicate over data link727 to the compliance module 725, that is configured to providecompliance control enforcement. This embodiment incorporates thefunctionality of the compliance server into a PBX and thus avoids havingto use two separate processing devices. The compliance module 725 andthe switch and control module 735 may execute on the same processor, oron different processors, which can be executing within a commonprocessing system. The facilities 727 may be a signaling link, so thatthat information about the wireless number, and whether the call isallowed to proceed is indicated via a signaling link, and no conferencecall leg is established between the switch and control module 735 andthe compliance module 725. The agent may use a workstation comprising acomputer 160 and a softphone 161 which are connected to the PBX 135 viafacilities 738. The facilities 738 may carry data as well as digitizedvoice.

In operation, the messaging flow may be as shown in FIG. 8. In FIG. 8,the messaging diagram 800 shows the agent's workstation comprising thecomputer 160 and phone 161. Further illustrated are the switch andcontrol module 735, the compliance module 725, and the PSTN 115.

The process may begin with the agent logging onto the compliance module725 in operation 820 using their computer 160. The compliance module 725now knows that the agent is available to dial a call, and may updateagent status information in operation 826. Next the compliance module725 may present the next wireless number for the agent to dial inmessage 828. This step may be optional, in that the compliance modulemay not offer the wireless number to dial, but simply receive thewireless number to dial in message 830.

Once the compliance module receives the number to dial, then inoperation 834 it performs the appropriate compliance processing toensure that the call originating to the wireless number meets all thecompliance requirements. If so, then in message 836 the compliancemodule 725 informs the switch and control module 735 to originate thecall for the indicated agent by dialing the number.

The switch and control module 735 receives the message 836 andestablishes an audio path 844 with the agent's phone and connects thiswith the call being established in message 848 using a conventional2-way switching resource 840. During the call set up process, variousin-band so-called comfort tones may be provided to the agent inoperation 846, so as to provide an indication to the agent of the callprogress. Assuming the called party answers the call setup in message848, the agent is connected to the called party.

During each step, the compliance module 725 may update information aboutthe status of the call and/or agent, in operations 845 and 849. Thecompliance module knows when a call is originated, the call's status,whether the agent is waiting for the call to connect to the calledparty, etc.

After the agent and the called party complete their conversation, theagent dispositions the call in operation 850. Dispositioning the callindicates to the compliance module that the agent has completed thecall, and the compliance module sends a command in message 854 to theswitch and control module 735 to release the call to the agent and thecalled party. In operation 856 the audio path to the agent's phone isremoved or otherwise the call leg is disconnected, and similarly thecall leg to the wireless call party is released in message 858.

Embodiment Four

Another embodiment is shown in FIG. 9. At a high level, this embodimentis based on the compliance server originating a call to the agent'sphone through the PBX. The agent then indicates the wireless number tothe PBX, which then originates a call leg to the wireless number andcreates a conference call. More specifically, the call leg to thewireless number is added to the call between the compliance server andthe agent. This allows the PBX to monitor the progress/status of thecall.

Furthermore, this embodiment allows the compliance server to function asa predictive dialer when the number to be dialed is a wireline numberand function as a compliance server if the number is a wireless number.

Turning to FIG. 9, the messaging diagram 900 illustrates in messages910-918 the messaging that occurs if the number to be dialed is awireline number. Later, messages 920-948 will be reviewed, and thisillustrates the messaging that occurs if the number to be dialed is awireless number. For sake of simplicity, the various operations in thecompliance server where it is able to update the agent's/call's statusis not shown in FIG. 9, as it was shown in the previous diagrams.

In operation, the agent may be presented with a number grid as shown inmessage 910 that may present various accounts and the numbers associatedtherewith. An agent may view the list and indicate the particular numberthey plan to dial. This is reflected in message 912 between the agent'scomputer and the compliance server 125. Because the number selected is awireline number, the compliance server, operating as a dialer,originates the call leg to the wireline number in message 913. A secondcall 914 is then established between the agent's phone 161 and thecalled party. After the call is completed, the agent may disposition thecall in operation 916 to the compliance server, which then releases thecall leg in message 917 to the called party, and the compliance serveralso releases the call leg to the agent's phone in message 918.

This process may be repeated, if the next number selected by the agentis a wireline number. This mode of dialing can be preview dialing. Otherembodiments may utilize other types of dialing appropriate for dialingwireline numbers.

Next, the processing of a wireless number is examined. Again, the agentis presented in message 920 a grid of numbers, from which the number todial is selected in message 922. The selected number is a wirelessnumber, and if the agent is not already aware of this, the complianceserver may inform the agent via a message on the computer display thatthe number is a wireless number and must be manually dialed.

After the agent indicates to the compliance server that the wirelessnumber they have selected in message 922, the compliance server 125 willestablish a call using messages 924 and 926 through the PBX 135 to theagent's phone. This results in a voice connection between the complianceserver and the agent's phone. In some embodiments, the compliance servermay provide an audible announcement to remind the user to dial thewireless number. The announcement could be, e.g., “Please dial 404 5551212”. This would correspond to the same wireless number previouslyselected by the agent in message 922.

This call that is established through the PBX is slightly different thana conventional call, in that the PBX is expecting to receive thewireless number from the agent, and will use that to establish aconference call and a call leg to that number and then join that callleg to the established call. This type of conference bridge allows theagent, as the answering party, to request a conference call.Consequently, in operation 928 the PBX prepares or expects to receivethe wireless number from the agent. The wireless number may betransmitted via DTMF tones, SIP INFO messages, or some other form as iswell known to those skilled in the art, in message(s) 930. The PBX mustknow that it should process the wireless number accordingly. Thus, forexample, if DTMF tones are used by the agent to convey the wirelessnumber, the PBX would have to attach a DTMF receiver to monitor thosetones.

The PBX upon receipt of the wireless number from the agent's phone thenoriginates a call leg to the wireless number in message 932. This isbridged on using a 3-way bridge in operation 934. The bridging of thewireless call leg can occur before the wireless call leg is originatedor just after the wireless call leg is originated. In either case, theresult shown is a three way call with call leg 938 between the agent andthe 3-way bridge 934, a call leg 936 between the compliance server andthe 3-way bridge, and a call leg 937 between the wireless party and the3-way bridge. This arrangement allows the compliance server to recordall aspects of the call from the origination of the wireless call leg,including any DTMF tones originating from the agent's phone (or comforttones provided to the agent), and call progress tones, announcements,etc.

As in the other embodiments, the call legs may be released in variousways. In the illustrated embodiment, the agent dispositions the call inmessage 940, which is received by the compliance server. In turn, thecompliance server releases the call leg to the PBX, and the PBX willrelease the call leg to the agent's phone. The process may repeat 952back to the next wireless number, as shown in FIG. 9 (but, which couldalso be a wireline number, which is not depicted in FIG. 9).

Exemplary Processing Device Architecture

FIG. 10 is an exemplary schematic diagram of a processing system 1000that may be used in an embodiment to practice the technologies disclosedherein, such as the PBX 135 or the compliance server 125. In general,the term “processing system” may be exemplified by, for example, butwithout limitation: a personal computer, server, desktop computer,tablets, smart phones, notebooks, laptops, distributed systems, servers,blades, gateways, switches, and the like, as well as any combination ofdevices or entities adapted to perform the functions described herein.

As shown in FIG. 10, the processing system 1000 may include one or moreprocessors 1001 that may communicate with other elements within theprocessing system 1000 via a bus 1005. The processor 1001 may beimplemented as one or more complex programmable logic devices (“CPLD”),microprocessors, multi-core processors, digital signal processors(“DSP”), system-on-a-chip (“SOC”), co-processing entities,application-specific integrated circuits (“ASIC”), field programmablegate arrays (“FPGA”), programmable logic arrays (“PLA”), hardwareaccelerators, other circuitry, or the like.

In one embodiment, the processing system 1000 may also include one ormore communications interfaces 1002 for communicating data via the localnetwork with various external devices. In other embodiments,communication may be via wired, optical, or wireless networks (or acombination thereof). The communication may use a variety of datatransmission protocols, such as fiber distributed data interface (FDDI),Ethernet, asynchronous transfer mode (“ATM”), or frame relay.

The input/output controller 1003 may also communicate with one or moreinput devices or peripherals using an interface 1004, such as, but notlimited to: a keyboard, a mouse, a touch screen/display input,microphone, pointing device, etc. The input/output controller 1003 mayalso communicate with output devices or peripherals, such as displays,printers, speakers, headsets, banner displays, etc.

The processor 1001 may be configured to execute instructions stored involatile memory 1006, non-volatile memory 1007, or other forms ofcomputer-readable storage media accessible to the processor 1001. Thevolatile memory 1006 may comprise various types of memory technologies,including, but not limited to: random access memory (“RAM”), dynamicrandom access memory (“DRAM”), static random access memory (“SRAM”), andother forms well known to those skilled in the art. The non-volatilememory 1007 may comprise various technologies, including, but notlimited to: storage media such as hard disks, floppy disks, read onlymemory (“ROM”), programmable read only memory (“PROM”), electricallyerasable read only memory (“EPROM”), flash memory, and other forms wellknown to those skilled in the art.

The non-volatile memory 1007 may store program code and data, which alsomay be loaded into the volatile memory 1006 at execution time.Specifically, the non-volatile memory 1007 may store one or morecomputer program modules, such as a compliance module 1009 containinginstructions for performing the process and/or functions associated withthe technologies disclosed herein, and related data 1010, and/oroperating system code 1008. In addition, the compliance module 1009 maygenerate or access the data 1010 in the non-volatile memory 1007, aswell as in the volatile memory 1006. The volatile memory 1006 and/ornon-volatile memory 1007 may be used to store other informationincluding, but not limited to: records, applications, programs, scripts,source code, object code, byte code, compiled code, interpreted code,machine code, executable instructions, or the like. These may beexecuted or processed by, for example, the processor 1001. These mayform a part of, or may interact with, the compliance module 1009 and/ordata 1010.

The technologies described herein may be implemented in various ways,including as computer program products comprising memory storinginstructions causing a processor to perform the operations associatedwith the above technologies. The computer program product comprises atangible, non-transitory computer readable storage medium storingapplications, programs, program modules, scripts, source code, programcode, object code, byte code, compiled code, interpreted code, machinecode, executable instructions, and/or the like (also referred to hereinas executable instructions, instructions for execution, program code,and/or similar terms). Such tangible, non-transitory computer readablestorage media include all the above identified media (including volatileand non-volatile media), but does not include a transitory, propagatingsignal. Non-volatile computer readable storage medium may specificallycomprise: a floppy disk, flexible disk, hard disk, magnetic tape,compact disc read only memory (“CD-ROM”), compact disc compactdisc-rewritable (“CD-RW”), digital versatile disc (“DVD”), Blu-ray™ disc(“BD”), any other non-transitory optical medium, and/or the like.Non-volatile computer-readable storage medium may also compriseread-only memory (“ROM”), programmable read-only memory (“PROM”),erasable programmable read-only memory (“EPROM”), electrically erasableprogrammable read-only memory (“EEPROM”), flash memory, and/or othertechnologies known to those skilled in the art.

Conclusion

Many modifications and other embodiments of the concepts andtechnologies set forth herein will come to mind to one skilled in theart having the benefit of the teachings presented in the foregoingdescriptions and the associated drawings. Therefore, it is to beunderstood that embodiments other than the embodiments disclosed hereinare intended to be included within the scope of the appended claims.Although specific terms may be employed herein, they are used in ageneric and descriptive sense only and not for purposes of limitation.

The invention claimed is:
 1. A system for ensuring compliance adherencefor a call to be placed to a called party from a contact center using awireless telephone number, the system comprising: a compliance serverconfigured to: determine whether the call to be placed to the calledparty is compliant with respect to at least one compliance requirement;and in response to the determining the call to be placed to the calledparty is compliant: inform an agent of the contact center of thewireless telephone number so that the agent can originate the call to beplaced to the called party using the wireless telephone number; and inresponse to receiving an indication that the agent has originated thecall to be placed to the called party: establish a first call legbetween the compliance server and a phone being used by the agent; andestablish a second call leg between the compliance server and a privatebranch exchange, wherein, upon receiving the wireless telephone number,the private branch exchange establishes a third call leg between theprivate branch exchange and a wireless device associated with the calledparty using the wireless telephone number, and the third call leg, thesecond call leg, and the first call leg are connected to form athree-way conference call between the phone being used by the agent, thecompliance server, and the wireless device associated with the calledparty.
 2. The system of claim 1, wherein the compliance server isconfigured to establish the agent has logged in prior to informing theagent of the wireless telephone number.
 3. The system of claim 1,wherein the indication that the agent has originated the call comprisesthe agent manually dialing digits on the phone being used by the agentcorresponding to the wireless telephone number.
 4. The system of claim3, wherein the compliance server is configured to determine the digitsdialed by the agent correspond to the wireless telephone number prior toestablishing the first call leg.
 5. The system of claim 1, wherein theindication that the agent has originated the call comprises the agentselecting the wireless telephone number on a display being used by theagent.
 6. The system of claim 1, wherein the compliance server isconfigured to establish a voice path between the compliance server and arecording system upon receiving the indication so that the call can berecorded by the recording system.
 7. A method for ensuring complianceadherence for a call to be placed to a called party from a contactcenter using a wireless telephone number, the method comprising thesteps of: determining by a compliance server whether the call to beplaced to the called party is compliant with respect to at least onecompliance requirement; and in response to the determining the call tobe placed to the called party is compliant: informing an agent of thecontact center by the compliance server of the wireless telephone numberso that the agent can originate the call to be placed to the calledparty using the wireless telephone number; and in response to receivingan indication that the agent has originated the call to be placed to thecalled party: establishing a first call leg between the complianceserver and a phone being used by the agent; establishing a second callleg between the compliance server and a private branch exchange;establishing a third call leg between the private branch exchange and awireless device associated with the called party using the wirelesstelephone number; and connecting the third call leg, the second callleg, and the first call leg to form a three-way conference call betweenthe phone being used by the agent, the compliance server, and thewireless device associated with the called party.
 8. The method of claim7 further comprising the step of establishing the agent has logged inprior to informing the agent of the wireless telephone number.
 9. Themethod of claim 7, wherein the indication that the agent has originatedthe call comprises the agent manually dialing digits on the phone beingused by the agent corresponding to the wireless telephone number. 10.The method of claim 9 further comprising the step of determining by thecompliance server the digits dialed by the agent correspond to thewireless telephone number prior to establishing the first call leg. 11.The method of claim 7, wherein the indication that the agent hasoriginated the call comprises the agent selecting the wireless telephonenumber on a display being used by the agent.
 12. The method of claim 7further comprising the step of establishing a voice path between thecompliance server and a recording system upon receiving the indicationso that the call can be recorded by the recording system.
 13. Anon-transitory computer-readable medium comprising computer-readableinstructions for ensuring compliance adherence for a call to be placedto a called party from a contact center using a wireless telephonenumber, the computer-readable instructions configured to, when executedby at least one computer processor residing on a compliance server,cause the at least one computer processor to: determine whether the callto be placed to the called party is compliant with respect to at leastone compliance requirement; and in response to the determining the callto be placed to the called party is compliant: inform an agent of thecontact center of the wireless telephone number so that the agent canoriginate the call to be placed to the called party using the wirelesstelephone number; and in response to receiving an indication that theagent has originated the call to be placed to the called party:establish a first call leg between the compliance server and a phonebeing used by the agent; and establish a second call leg between thecompliance server and a private branch exchange, wherein, upon receivingthe wireless telephone number, the private branch exchange establishes athird call leg between the private branch exchange and a wireless deviceassociated with the called party using the wireless telephone number,and the third call leg, the second call leg, and the first call leg areconnected to form a three-way conference call between the phone beingused by the agent, the compliance server, and the wireless deviceassociated with the called party.
 14. The non-transitorycomputer-readable medium of claim 13, wherein the computer-readableinstructions, when executed, are configured to cause the at least onecomputer processor to establish the agent has logged in prior toinforming the agent of the wireless telephone number.
 15. Thenon-transitory computer-readable medium of claim 13, wherein theindication that the agent has originated the call comprises the agentmanually dialing digits on the phone being used by the agentcorresponding to the wireless telephone number.
 16. The non-transitorycomputer-readable medium of claim 15, wherein the computer-readableinstructions, when executed, are configured to cause the at least onecomputer processor to determine the digits dialed by the agentcorrespond to the wireless telephone number prior to establishing thefirst call leg.
 17. The non-transitory computer-readable medium of claim13, wherein the indication that the agent has originated the callcomprises the agent selecting the wireless telephone number on a displaybeing used by the agent.
 18. The non-transitory computer-readable mediumof claim 13, wherein the computer-readable instructions, when executed,are configured to cause the at least one computer processor to establisha voice path between the compliance server and a recording system uponreceiving the indication so that the call can be recorded by therecording system.
 19. A method for ensuring compliance adherence for acall to be placed to a called party from a contact center using awireless telephone number, the method comprising the steps of:determining whether the call to be placed to the called party iscompliant with respect to at least one compliance requirement; and inresponse to the determining the call to be placed to the called party iscompliant: informing an agent of the contact center of the wirelesstelephone number so that the agent can originate the call to be placedto the called party using the wireless telephone number; and in responseto receiving an indication that the agent has originated the call to beplaced to the called party: establishing a first call leg between thecompliance server and a private branch exchange; establishing a secondcall leg between the private branch exchange and a phone being used bythe agent; establishing a third call leg between the private branchexchange and a wireless device associated with the called party usingthe wireless telephone number; and connecting the third call leg, thesecond call leg, and the first call leg to form a three-way conferencecall between the phone being used by the agent, the compliance server,and the wireless device associated with the called party.
 20. The methodof claim 19, wherein the first call leg comprises a one-way voice pathfrom the private branch exchange to the compliance server.
 21. Themethod of claim 19, wherein the indication that the agent has originatedthe call comprises the agent selecting the wireless telephone number ona display being used by the agent.
 22. The method of claim 19 furthercomprising the step of establishing a voice path between the complianceserver and a recording system upon receiving the indication so that thecall can be recorded by the recording system.
 23. A non-transitorycomputer-readable medium comprising computer-readable instructions forensuring compliance adherence for a call to be placed to a called partyfrom a contact center using a wireless telephone number, thecomputer-readable instructions configured to, when executed by at leastone computer processor residing on a compliance server, cause the atleast one computer processor to: determine whether the call to be placedto the called party is compliant with respect to at least one compliancerequirement; and in response to the determining the call to be placed tothe called party is compliant: inform an agent of the contact center ofthe wireless telephone number so that the agent can control originatingthe call to be placed to the called party using the wireless telephonenumber; and in response to receiving an indication from that the agentoriginated the call to be placed to the called party: establish a firstcall leg between the compliance server and a private branch exchange;and establish a second call leg between the private branch exchange anda phone being used by the agent, wherein, upon receiving the wirelesstelephone number, the private branch exchange establishes a third callleg between the private branch exchange and a wireless device associatedwith the called party using the wireless telephone number, and the thirdcall leg, the second call leg, and the first call leg are connected toform a three-way conference call between the phone being used by theagent, the compliance server, and the wireless device associated withthe called party.
 24. The non-transitory computer-readable medium ofclaim 23, wherein the first call leg comprises a one-way voice path fromthe private branch exchange to the compliance server.
 25. Thenon-transitory computer-readable medium of claim 23, wherein theindication that the agent has originated the call comprises the agentselecting the wireless telephone on a display being used by the agent.26. The non-transitory computer-readable medium of claim 23, wherein thecomputer-readable instructions, when executed, are configured toestablish a voice path between the compliance server and a recordingsystem upon receiving the indication so that the call can be recorded bythe recording system.